ᵉShare DevOps Dashboard

Executive

Team:

Type:

📖 How are executive metrics calculated? ▼

Completion Rate: Work items in Done or Closed state ÷ Total work items × 100.

In Progress: Work items with state "In Progress".

Open Bugs: Bugs not in Done, Closed, or Removed state.

Blocked: Work items with "blocked" in their Tags field.

Unassigned: Open work items (not Done/Closed/Removed) with no Assigned To value.

Time Period:

👇 Click on a team card below to view details

Team Details

👥 Engineer Workload

Filter:

All States ▼

All Priorities ▼

Select All

1 - Critical 2 - High 3 - Medium 4 - Low

All Types ▼

Select All

Bug Task Delivery Slice Feature Issue Epic Key Result Objective

Filter by Engineer:

All Engineers ▼

Select engineers above to view work item details

📊 Effort Categorization

By Type

All Types ▼

Select All

Bug Task Delivery Slice Feature Issue Epic

By State

All States ▼

Select All

New Triaged To Do In Progress Ready For Review Done Closed Removed

By Priority

All Priorities ▼

Select All

1 - Critical 2 - High 3 - Medium 4 - Low

By Assigned To

All Members ▼

By Iteration

All Iterations ▼

📊 How is effort calculated? ▼

Effort: Sum of the "Effort" field on each work item (in person-days).

By Type: Effort is shown separately per work item type to avoid double-counting. For example, if a Delivery Slice has 5d effort and its child Tasks also have effort, they are counted separately.

Capacity: Number of team members × working days in the selected period (excludes weekends).

Utilization: Total Effort ÷ Capacity × 100%. Values over 100% indicate over-commitment.

Note: This calculation assumes all team members are available full-time. PTO, holidays, and part-time allocations are not factored in.

Work Items

ID	Type	Title	State	Priority	Assigned To	Iteration	Effort

Team:

State:

All States ▼

Select All

New Triaged To Do In Progress Ready For Review Done Closed Removed

📖 How is customer impact tracked? ▼

Customer Work Items: Issues and Bugs with the "Customers" field populated.

Customer Count: Each unique value in the Customers field is counted separately.

Multi-Customer Items: Work items affecting multiple customers (comma-separated in the Customers field).

Resolution Time: Time from Created Date to Closed Date for resolved items.

Date Range:

Bug Type:

All Types ▼

Select All

Customer Related Product Quality Technical & Infrastructure

Priority:

All Priorities ▼

Select All

1 - Critical 2 - High 3 - Medium 4 - Low

State:

All States ▼

Select All

New Triaged To Do In Progress Ready For Review Done Closed Removed

📖 How are bug metrics calculated? ▼

Active bugs: Bugs that were active during the selected period (created before period end AND not closed before period start).

Spread effort: Effort is distributed proportionally across each bug's lifetime. E.g., a 15-day bug open for 50 days contributes 15×(7/50)=2.1 days to a 7-day period.

Utilization %: Spread effort ÷ working days in period × 100. Shows what % of an engineer's time was spent on bugs.

Created vs Closed: Bugs created or closed within the selected date range. "Closed" includes both Done (code changes) and Closed (no code changes) states.

Bug Trend by Week

Bug Categorization

Bug Effort

Effort Estimate vs Actual

📖 How is bug effort tracked? ▼

Estimate (Bug Effort): Initial estimate entered by Bug Owner when bug is created.

Actual (Effort Rollup): Sum of effort from child tasks, entered by engineers as they work.

Divergence: Actual − Estimate. Positive = took longer than estimated, Negative = took less.

Variance: The divergence as a percentage of the estimate.

Items by Release

Click bar to select · Ctrl+Click for multi-select

Items by Release Click bar to select · Ctrl+Click for multi-select

Feature Roadmap

Link to ADO Feature Backlog

Parent Type:

State:

All States ▼

Select All

New Triaged To Do In Progress Ready For Review Done Closed Removed

Team:

Bug Type:

State:

All States ▼

Select All

New Triaged To Do In Progress Ready For Review Done Closed Removed

📊 Data Source Validation

📖 What is Data Source Validation? ▼

Purpose: Ensures the dashboard accurately reflects the source CSV data from Azure DevOps.

CSV Source: The count and breakdown of records as read from the input CSV file during generation.

Dashboard: The count and breakdown computed from the workItems array in the browser.

Match Status: ✓ indicates values match exactly, ✗ indicates a discrepancy that needs investigation.

Data Quality Checks

📖 What makes data "quality"? ▼

Fully Classified Bug: A bug with Bug Type, Feature, and Component all set.

Tasks Missing Effort: Tasks where engineers haven't logged their actual effort (Effort field is empty or 0).

Bugs Without Tasks: Bugs with estimates but no task breakdown (work not yet planned).

Orphan Tasks: Tasks not linked to any parent work item.

Same-Type Parent: Work items whose parent is the same type (e.g., Task under Task) - unusual hierarchy.

Cross-Team Assignment: Work item assigned to someone not in the team (based on Area Path vs Org Chart).

Unknown Assignee: Work item assigned to someone not found in any team in the Org Chart.

Team:

Type:

State:

All States ▼

Select All

New Triaged To Do In Progress Ready For Review Done Closed Removed

Team Details

👥 Engineer Workload

📊 Effort Categorization

Work Items

Bug Categorization

Bug Effort

Effort Estimate vs Actual

Items by Release

Feature Roadmap

📊 Data Source Validation

Data Quality Checks

Delivery Slices